Client Profile
The client is a US-headquartered financial institution providing commercial banking, treasury, and wealth management services to mid-market corporate clients. The organisation employs approximately 6,800 staff, the majority of whom are knowledge workers in finance, risk, operations, compliance, and client services roles. Its Microsoft footprint includes a three-year Enterprise Agreement covering M365 E3 and E5, Windows, and Unified Support.
The institution has historically been a conservative technology adopter, preferring proven capability over leading-edge deployment. Its Microsoft 365 utilisation is high relative to sector benchmarks — Exchange, Teams, SharePoint, and OneDrive are all deeply embedded — but it had not yet explored AI tooling at an enterprise scale.
The Challenge
Microsoft's renewal proposal arrived at a total three-year value of $10.8M. Embedded within the proposal were two line items that had not been present in the prior agreement: a 2,000-seat Microsoft 365 Copilot deployment at $30 per user per month ($2.16M over three years) and a Unified Support fee increase of approximately $144,000 per year ($432,000 over three years), justified by the higher total contract value under the proposed renewal.
The institution had not requested a Copilot deployment. Microsoft's account team presented it as a "strategic investment in productivity" and suggested it was available at a preferential rate as part of the renewal bundle. The Unified Support increase was presented as automatic — a function of the contractual percentage-of-total-software-value calculation that governs Unified Support pricing.
— CTO, US financial institution client
Two additional issues were identified during the pre-negotiation review. The institution's existing Unified Support agreement was co-terminous with the EA, meaning both agreements were up for renewal simultaneously. Co-termination eliminates the independent negotiating leverage each contract creates — a structural disadvantage for the customer. Additionally, the institution had E5 licences assigned to approximately 900 users whose roles (primarily administrative and back-office support) did not require the advanced E5 feature set.
The Approach
Redress Compliance was retained seven weeks before the renewal date. The engagement focused on three parallel workstreams: Copilot demand analysis and position construction; Unified Support decoupling and renegotiation; and E5-to-E3 rationalisation for the back-office population.
Copilot: Demand Analysis and Counter-Proposal
A structured Copilot demand assessment was conducted across the 6,800-seat estate, covering three questions: which user populations had a clearly articulated use case for AI-assisted productivity tooling; what measurable productivity metric would justify the investment; and what timeline was realistic for achieving adoption at scale in a regulated financial institution.
The assessment concluded that a defensible business case existed for approximately 400 seats — predominantly in document-intensive compliance and research roles — but that the 2,000-seat deployment proposed by Microsoft was not supportable on current usage patterns or articulated business needs. A counter-proposal was constructed for a 400-seat Copilot pilot over the first year of the new EA, with an option to expand in years two and three based on defined adoption metrics, at pre-agreed pricing.
Unified Support: Decoupling and Renegotiation
The Unified Support agreement was separated from the EA renewal and treated as a standalone negotiation. By decoupling the two contracts, the institution recovered independent leverage over each. The Unified Support renewal was benchmarked against Microsoft's published support tier structure and against independently sourced data on comparable support agreements for financial institutions at the same seat count.
The analysis demonstrated that the proposed Unified Support fee represented a 19% increase over the prior year's rate, while the institution's actual support consumption (measured by case volume and severity distribution) had remained flat. A counter-proposal was constructed for a fee at 4% below the prior year's rate, justified by static consumption and a documented reduction in critical incident volume over the prior 12 months.
E5 Rationalisation
The E5 review identified 900 back-office users (primarily data entry, administrative support, and facilities management roles) who were carrying E5 licences without activating any E5-specific features. A transition to E3 was proposed for this population, generating a saving of approximately $21 per user per month.
| Workstream | Microsoft Proposal | Negotiated Outcome | 3-Year Saving |
|---|---|---|---|
| Copilot | 2,000 seats × $30/user/mo | 400-seat pilot, year 1 only | $1,728,000 |
| Unified Support | +19% vs. prior year | -4% vs. prior year | $536,400 |
| E5 → E3 (900 users) | E5 across estate | E3 for 900 back-office users | $680,400 |
The Outcome
The institution signed a restructured three-year EA at $8.2M, against Microsoft's opening proposal of $10.8M — a reduction of $2.6M (24%). The Copilot pilot was structured with a defined 12-month evaluation period, pre-agreed expansion pricing, and an explicit contractual provision allowing the institution to exit the Copilot commitment at the end of year one if adoption metrics were not met.
The Unified Support agreement was renewed at a fee 4% below the prior year — the first time in the institution's history that a Unified Support renewal had resulted in a year-on-year fee reduction. The E5-to-E3 migration for 900 back-office users was completed within 45 days of the EA signing, with no reported productivity impact.
The institution also established a formal Copilot governance framework, including a defined set of adoption KPIs, a quarterly review process, and a clear decision protocol for the year-two expansion decision. This structure meant that any future Copilot investment would be driven by evidence of value rather than Microsoft's commercial cycle.
Facing a Microsoft Copilot or Unified Support upsell at renewal?
Independent analysis and negotiation support — no commercial interest in what you buy.Key Takeaways
Copilot should be treated as a new investment decision, not a renewal line item
Microsoft's strategy is to embed Copilot into the EA renewal as though it is an extension of existing entitlements. It is not. At $30 per user per month, a 2,000-seat Copilot deployment represents a $720,000 annual incremental spend that warrants independent business case evaluation, ROI modelling, and adoption planning. Organisations that accept Copilot at renewal as a bundled item without this analysis consistently find that adoption rates at month 12 are far below the committed seat count.
Co-terminous EA and Unified Support renewals cost you leverage
When your EA and Unified Support agreements expire at the same time, Microsoft's account team bundles them into a single commercial proposal and uses each to justify the other. Separating the two negotiations — ideally through deliberate off-cycle renewal of Unified Support — restores independent leverage over each contract. If co-termination cannot be avoided, treating each agreement as a separate negotiation within the same process achieves a similar effect.
Unified Support pricing is negotiable despite Microsoft's framing
Microsoft presents Unified Support pricing as a formula (a fixed percentage of total software value) that leaves no room for negotiation. In practice, the absolute fee level, the scope of coverage, and the support tier structure are all negotiable, particularly when the customer has documented evidence of flat or declining support consumption. An institution that accepts the automatic fee uplift without challenge at each renewal will pay materially more over a multi-year relationship than one that treats Unified Support as an independent commercial negotiation.